TR
11111

COURSE INTRODUCTION AND APPLICATION INFORMATION

se.cs.ieu.edu.tr

Course Name
Code
Semester
Theory
(hour/week)
Application/Lab
(hour/week)
Local Credits
ECTS
Spring
Prerequisites
None
Course Language
Course Type
Required
Course Level
-
Mode of Delivery -
Teaching Methods and Techniques of the Course Problem Solving
Application: Experiment / Laboratory / Workshop
Course Coordinator -
Course Lecturer(s) -
Assistant(s) -
Course Objectives
Learning Outcomes The students who succeeded in this course;
  • Identify and define the information that is needed to design a database schema for a database application,
  • Create conceptual and physical database designs for a management information system by drawing the E/RDiagram and performing the normalization of relations,
  • Understand the core terms, concepts, and tools of relational database management systems,
  • Query a database using SQL,
  • Implement database applications by properly managing concurrent transactions,
  • Finetune a database design to improve the performance of applications by the use of beneficial indexes and additional data structures conforming to the characteristics of applications running on them.
Course Description

 



Course Category

 Core Courses
X
Major Area Courses
Supportive Courses
Media and Managment Skills Courses
Transferable Skill Courses

 

WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES

Week Subjects Required Materials
1 Introduction to Database Systems, Relational Data Model, SemistructuredData Model J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 1, Ch. 2.1, 2.2, 2.3, Ch. 11.1, 11.2, 11.3)
2 EntityRelationship Data Model J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 4.1, 4.2, 4.3, 4.4, 4.5, 4.6)
3 Introduction to Relational Algebra and Design of Relational Databases, Functional Dependencies J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 2.4, 3.1, 3.2, 3.3, 3.4, 3.5)
4 Design of Relational Databases, Multivalued Dependencies J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 3.6, 3.7)
5 Relational Algebra J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 5.1)
6 Introduction to SQL (Part I) J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 6.1, 6.2, 6.3, 6.4.1, 6.4.2)
7 Introduction to SQL (Part II) J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 5.2, 6.4, 6.5)
8 Midterm
9 Constraints and Triggers J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 7)
10 SQL Programming: Embedded SQL, PSM ( PL/SQL) J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 9.3, 9.4)
11 SQL Programming: CLI, JDBC, PHP/PEAR J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 9.1, 9.2, 9.5, 9.6, 9.7)
12 Transactions, Views, Indexes J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 6.6, 8.1, 8.2, 8.3, 8.4, 8.5)
13 SQL Authorization J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 10.1)
14 Logical Query Languages (Datalog) and SQL Recursion J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 5.3, 5.4, 10.2)
15 Warehousing, Data Cubes, Data Mining J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 10.6, 10.7)
16 Review of the Semester  
Course Notes/Textbooks Textbook "J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008" and course slides (Book’s URL: http://wwwdb.stanford.edu/~ullman/fcdb.html)
Suggested Readings/Materials Reference Book: Silberschatz et. al., Database System Concepts, 4th ed., McGrawHill, 2002.

 

EVALUATION SYSTEM

Semester Activities Number Weigthing
Participation
1
10
Laboratory / Application
7
15
Field Work
Quizzes / Studio Critiques
5
15
Portfolio
Homework / Assignments
15
0
Presentation / Jury
Project
Seminar / Workshop
Oral Exam
Midterm
1
25
Final Exam
1
35
Total

Weighting of Semester Activities on the Final Grade
65
Weighting of End-of-Semester Activities on the Final Grade
35
Total

ECTS / WORKLOAD TABLE

Semester Activities Number Duration (Hours) Workload
Course Hours
(Including exam week: 16 x total hours)
16
3
48
Laboratory / Application Hours
(Including exam week: 16 x total hours)
16
2
Study Hours Out of Class
15
3
Field Work
Quizzes / Studio Critiques
4
2
Portfolio
Homework / Assignments
15
2
Presentation / Jury
Project
Seminar / Workshop
Oral Exam
Midterms
1
17
Final Exams
1
20
    Total
200

 

COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP

#
 Program Competencies/Outcomes
* Contribution Level
1
2
3
4
5
1 Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute
2 Be able to design and analyze software at component, subsystem, and software architecture level X
3 Be able to develop software by coding, verifying, doing unit testing and debugging X
4 Be able to verify software by testing its behaviour, execution conditions, and expected results
5 Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation
6 Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically X
7 To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning
 X
8 Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes X
9 Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance X
10 To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software X
11 To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering
12 Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering
13

Be able to use a foreign language to follow related field publications and communicate with colleagues

 X

*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest

 

İzmir Ekonomi Üniversitesi | Sakarya Caddesi No:156, 35330 Balçova - İZMİR Tel: +90 232 279 25 25 | webmaster@ieu.edu.tr | YBS 2010